Uploading via QA·GUI

Whilst uploading via server-side analysis is the recommended approach for non-Solo projects, it is also possible to upload results from QA·GUI.

Results can be uploaded regardless of whether or not your project is a Unified project, although you will not be able to share the results with other users as long as the project is not Unified.

There is no need to upload the whole code project in the case of a Solo project. For example, if the review is to be focused on just three or four files, then upload only those files, using the following option:

Helix QAC Dashboard menu : Upload Results : Upload Selected Files to Helix QAC Dashboard

However, in the case of a non-Solo project, care should be taken to upload the full project, using the following option:

Helix QAC Dashboard menu : Upload Results : Upload Project to Helix QAC Dashboard

To upload you must already be logged into Helix QAC Dashboard and have "Upload" permissions.

This is because, if only selected files are uploaded, this affects the inheritance aspect of the snapshot sequence representing the project history. Trend reports will be affected by the gap in data, but, more importantly, Helix QAC Dashboard suppressions may also be affected. Suppressions against diagnostics in a file are, by default, inherited by the next snapshot, and, if that file is not uploaded as part of the snapshot, then the suppressions will not be inherited by either this snapshot or any subsequent snapshots.

Refer to The Helix QAC Dashboard Menu for how to use the above options, for the Upload Results dialog. Normally, all you need to specify is the name of the snapshot. If the source code has been checked into the version control system, leave the Upload Source selection as None.